Triple
T16453373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cohen Group |
E399609
|
entity |
| Predicate | hasRevolvingDoorConnections |
P122848
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Cohen Group, hasRevolvingDoorConnections, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevolvingDoorConnections Context triple: [The Cohen Group, hasRevolvingDoorConnections, true]
-
A.
hasNumberOfEntrances
Indicates the relationship that specifies how many entrances an entity possesses.
-
B.
hasSeparateEntrances
Indicates that the related entities each have their own distinct entrance, rather than sharing a common one.
-
C.
hasEndDoors
Indicates that an object or structure is equipped with doors located at one or more of its ends.
-
D.
hasShelteredEntrances
Indicates that an entity provides one or more entrances that are covered or protected from weather or external exposure.
-
E.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ce259d88190803930051409d72c |
completed | April 18, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.