Triple
T29210813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inbam |
E740540
|
entity |
| Predicate | belongsToTripartiteDivision |
P32197
|
FINISHED |
| Object | Aram–Porul–Inbam |
—
|
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: Aram–Porul–Inbam | Statement: [Inbam, belongsToTripartiteDivision, Aram–Porul–Inbam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToTripartiteDivision Context triple: [Inbam, belongsToTripartiteDivision, Aram–Porul–Inbam]
-
A.
isPartOfDivision
Indicates that one entity belongs to, or is contained within, a specific division of a larger organizational or structural unit.
-
B.
hasDivisionCounterpart
Indicates that one entity serves as the division-level equivalent or counterpart of another entity within an organizational or structural hierarchy.
-
C.
belongsToDivision
chosen
Indicates that an entity is a member of, or is organizationally assigned to, a specific division.
-
D.
hasThirdDivision
Indicates that an entity possesses or is associated with a third-level division or subdivision within a hierarchical structure.
-
E.
ownsDivision
Indicates that one entity has legal or controlling ownership over a specific division of another entity or organization.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 28, 2026, 12:11 p.m.