Triple
T23038170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malcolm Scott Carpenter |
E573663
|
entity |
| Predicate | wasSecond |
P150744
|
FINISHED |
| Object | second American to orbit the Earth |
—
|
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: second American to orbit the Earth | Statement: [Malcolm Scott Carpenter, wasSecond, second American to orbit the Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSecond Context triple: [Malcolm Scott Carpenter, wasSecond, second American to orbit the Earth]
-
A.
secondedBy
Indicates that an initial proposal, motion, or action by one entity is formally supported or endorsed by another entity as a second.
-
B.
wasSecondPresidentialElection
Indicates that an event was the second presidential election held within a given political system or jurisdiction.
-
C.
wasA
Indicates that an entity previously had a certain role, type, or classification in the past.
-
D.
hasSecond
Indicates that one entity is the second item, position, or element in an ordered sequence or pair relative to another entity.
-
E.
hadSecondInCommand
Indicates that one entity had another entity serving as its second-in-command or primary subordinate leader.
- F. None of above. chosen
Provenance (4 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f185111f0881908991fcd6cdc7db9f |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:53 p.m.