Triple
T1114232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Petty Bench |
E11059
|
entity |
| Predicate | hasPeer |
P6215
|
FINISHED |
| Object | First Petty Bench |
—
|
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: First Petty Bench | Statement: [Second Petty Bench, hasPeer, First Petty Bench]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeer Context triple: [Second Petty Bench, hasPeer, First Petty Bench]
-
A.
peerOf
chosen
Indicates that two entities hold equivalent or comparable status, role, or standing within the same context or system.
-
B.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
C.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
D.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
E.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.