Triple
T32448409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fan Ju |
E829208
|
entity |
| Predicate | wasInitiallyInServiceOf |
P23909
|
FINISHED |
| Object | State of Wei |
—
|
NE NERFINISHED |
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: State of Wei | Statement: [Fan Ju, wasInitiallyInServiceOf, State of Wei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasInitiallyInServiceOf Context triple: [Fan Ju, wasInitiallyInServiceOf, State of Wei]
-
A.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
B.
commissionedInService
chosen
Indicates that an entity was formally brought into active service or duty within a particular organization, role, or context.
-
C.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
D.
historicallyServedBy
Indicates that an entity was provided with services or support by another entity during a past period of time.
-
E.
militaryUnitTypeServed
Indicates that an entity served in, or was a member of, a specific type of military unit.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e822a88190a7b32d03127a2025 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:56 a.m.