Triple
T31021678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIM |
E790465
|
entity |
| Predicate | typicalIssuerStage |
P90116
|
FINISHED |
| Object | early‑stage |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: early‑stage | Statement: [AIM, typicalIssuerStage, early‑stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalIssuerStage Context triple: [AIM, typicalIssuerStage, early‑stage]
-
A.
isAStageOf
Indicates that one entity represents a particular phase, step, or period within the development, progression, or lifecycle of another entity.
-
B.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
C.
isOftenStagedAs
Indicates that one work, story, or event is frequently presented or performed in the form of another specified medium or production type (such as a play, opera, or film).
-
D.
coreStageType
chosen
Indicates the specific kind or classification of a core stage within a larger process, system, or lifecycle.
-
E.
stagedBy
Indicates that an event, performance, or production is organized, directed, or put on by a particular agent or entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:58 p.m.