Triple
T38218659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Colonial Marine Corps |
E1010749
|
entity |
| Predicate | notableBattleInFiction |
P191433
|
FINISHED |
| Object | Hadley’s Hope incident on LV-426 |
E1501867
|
NE 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: Hadley’s Hope incident on LV-426 | Statement: [United States Colonial Marine Corps, notableBattleInFiction, Hadley’s Hope incident on LV-426]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBattleInFiction Context triple: [United States Colonial Marine Corps, notableBattleInFiction, Hadley’s Hope incident on LV-426]
-
A.
notableBattleRecognized
Indicates that a particular battle is formally acknowledged or recognized as notable in relation to the subject.
-
B.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
-
C.
notableBattlefield
Indicates that a location is recognized as the site of a historically significant battle or military engagement.
-
D.
notableBattleDuringReign
Indicates that a particular battle is notably associated with and occurred during the time span of a specific ruler’s reign.
-
E.
battleFoughtBy
chosen
Indicates that a specific battle was fought by a particular participant or group of participants.
- F. None of above.
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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41854f555081909708ff677a965190 |
completed | June 28, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.