Triple
T9485752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilo |
E228755
|
entity |
| Predicate | hasRelationships |
P88389
|
FINISHED |
| Object | complex relationships |
—
|
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: complex relationships | Statement: [Tilo, hasRelationships, complex relationships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationships Context triple: [Tilo, hasRelationships, complex relationships]
-
A.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
B.
hasKeyRelationship
Indicates a relationship where one entity serves as a key (e.g., identifier, access token, or primary reference) that grants access to, controls, or uniquely identifies another entity.
-
C.
hasNeighborRelationshipWith
Indicates that one entity is located adjacent to or directly next to another entity, sharing a neighbor relationship.
-
D.
showsRelationshipWith
Indicates that one entity visually or explicitly presents or demonstrates its connection or association with another entity.
-
E.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
- 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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd804fb2b4819084c7f5a842dbe5a6 |
completed | April 1, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:55 p.m.