Triple
T29389298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PrintAttributes |
E745332
|
entity |
| Predicate | immutableAfterBuild |
P90874
|
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: [PrintAttributes, immutableAfterBuild, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: immutableAfterBuild Context triple: [PrintAttributes, immutableAfterBuild, true]
-
A.
notRebuiltAfter
Indicates that an entity was destroyed or damaged and has not been reconstructed or restored after a specified event or point in time.
-
B.
laterRebuiltAs
Indicates that one entity was reconstructed or redeveloped at a later time to become or be replaced by another specific entity.
-
C.
implementedAfter
Indicates that one implementation occurs or is introduced only after another specified implementation has taken place or been completed.
-
D.
isImmutable
chosen
Indicates that the referenced entity cannot be changed or modified after it has been created.
-
E.
wasBuilt
Indicates that one entity constructed, created, or assembled another entity, typically at a specific time or over a period.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d578608190962d35116a01420c |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:41 p.m.