Triple
T36379465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chunqiu |
E896003
|
entity |
| Predicate | recordsEventsOf |
P182011
|
FINISHED |
| Object | State of Lu |
—
|
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 Lu | Statement: [Chunqiu, recordsEventsOf, State of Lu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsEventsOf Context triple: [Chunqiu, recordsEventsOf, State of Lu]
-
A.
recordsEventsVia
Indicates that one entity captures or logs events through the mechanism, system, or medium provided by another entity.
-
B.
recordEvent
Indicates that an entity logs or stores information about a specific occurrence or action as an event.
-
C.
recordsOn
Indicates that one entity documents, stores, or logs information about another entity on a particular medium, system, or date.
-
D.
eventHistory
chosen
Indicates a relationship where an entity is associated with a chronological record of past events or occurrences involving it.
-
E.
recordsWith
Indicates that one entity keeps or maintains documented information about another entity or event.
- 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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:10 p.m.