Triple
T15084911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabouret Berger |
E360246
|
entity |
| Predicate | canAlsoServeAs |
P2819
|
FINISHED |
| Object | side table |
—
|
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: side table | Statement: [Tabouret Berger, canAlsoServeAs, side table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canAlsoServeAs Context triple: [Tabouret Berger, canAlsoServeAs, side table]
-
A.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
-
B.
canAlsoBe
chosen
Indicates that something has an additional possible state, role, or classification beyond its primary one.
-
C.
alsoServedBy
Indicates that the same service, function, or role is additionally provided or fulfilled by another entity alongside the primary one.
-
D.
alsoServes
Indicates that an entity, in addition to its primary role or function, provides service or support to another specified entity or group.
-
E.
possiblyServedAs
Indicates that an entity may have held or fulfilled a particular role, position, or function, but this service is uncertain or not definitively confirmed.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00275cfa88190a13fe20b585d9fcb |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:03 a.m.