Triple
T23778541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year of the Tiger |
E587743
|
entity |
| Predicate | governingElementExample |
P153903
|
FINISHED |
| Object | Water Tiger |
—
|
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: Water Tiger | Statement: [Year of the Tiger, governingElementExample, Water Tiger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingElementExample Context triple: [Year of the Tiger, governingElementExample, Water Tiger]
-
A.
governingBodyExample
Indicates that the subject entity serves as an example or instance of a governing body for the object entity.
-
B.
governingDocumentMentioned
Indicates that a governing document is referenced or cited in relation to the entities involved.
-
C.
governingBodyIncludes
Indicates that a governing body has a particular entity as one of its members or constituent parts.
-
D.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
-
E.
definesElement
Indicates that one entity specifies or determines the nature, structure, or identity of another entity as its defining element.
- F. None of above. chosen
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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c629f0c08190baccce71ebc72650 |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15ed138f88190a8ae555422978908 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 17, 2026, 7:16 p.m.