Triple
T1130013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Single-A |
E23006
|
entity |
| Predicate | developmentStage |
P16858
|
FINISHED |
| Object | early professional career 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 professional career stage | Statement: [Single-A, developmentStage, early professional career stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentStage Context triple: [Single-A, developmentStage, early professional career stage]
-
A.
developmentStart
Indicates the point in time or event when the development process of something begins.
-
B.
investmentStage
Indicates the phase or maturity level a company or project is in with respect to receiving investment or funding.
-
C.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
D.
developmentLevel
chosen
Indicates the degree or stage of progress, advancement, or maturity that something has reached in its growth or evolution.
-
E.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb48de2081909a0dce005b1c9df1 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.