Triple
T6497045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inca forces |
E148783
|
entity |
| Predicate | requiredServiceFrom |
P10395
|
FINISHED |
| Object | adult males |
—
|
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: adult males | Statement: [Inca forces, requiredServiceFrom, adult males]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredServiceFrom Context triple: [Inca forces, requiredServiceFrom, adult males]
-
A.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
B.
serviceUserRequirement
Indicates that a user has a specific requirement or need that a service is expected to fulfill.
-
C.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
D.
requiresApplicationTo
Indicates that one entity can only access, use, or obtain another entity if a formal application or request process is completed.
-
E.
requiresActionFrom
chosen
Indicates that one entity is obligated to perform or initiate some action in response to or as a consequence of another entity or situation.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:41 p.m.