Triple
T21698989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchu Mile road march |
E535602
|
entity |
| Predicate | eligibilityForAward |
P56760
|
FINISHED |
| Object | successful completion of the march |
—
|
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: successful completion of the march | Statement: [Manchu Mile road march, eligibilityForAward, successful completion of the march]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibilityForAward Context triple: [Manchu Mile road march, eligibilityForAward, successful completion of the march]
-
A.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
B.
canBeAwarded
chosen
Indicates that an entity is eligible to receive or be granted a particular award, prize, or honor.
-
C.
isAwardedWithin
Indicates that an award or recognition is granted to an entity within a specified context, scope, or time frame.
-
D.
canAward
Indicates that one entity has the authority or ability to grant an award, honor, or recognition to another entity.
-
E.
canBeAwardedTo
Indicates that something is eligible to receive or be granted a particular award, honor, or recognition.
- 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_69e0c46a6ee481908836e1420fb78c9b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b7de9888190bbca7717a32f9888 |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:45 p.m.