Triple
T27559643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surface 3 Type Cover |
E695738
|
entity |
| Predicate | isDetachable |
P107015
|
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: [Surface 3 Type Cover, isDetachable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDetachable Context triple: [Surface 3 Type Cover, isDetachable, true]
-
A.
canDetach
chosen
Indicates that one entity is able to be separated or removed from another entity or from a larger whole.
-
B.
hasDetachment
Indicates that an entity is separated, disconnected, or removed from another entity or its original position.
-
C.
hasDetachableControllers
Indicates that an object is equipped with controllers that can be physically removed or separated from its main body.
-
D.
isExpendable
Indicates that the entity can be sacrificed, discarded, or removed without causing unacceptable loss or consequence to the overall system or objective.
-
E.
canDetachHead
Indicates that an entity has the ability to remove or separate its head from the rest of its body.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62fb839fc81909bdfc34aac33dcf6 |
completed | May 2, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:38 p.m.