Triple
T13819352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Square and Compasses |
E332095
|
entity |
| Predicate | hasSymbolicOrigin |
P3654
|
FINISHED |
| Object | operative stonemasonry tools |
—
|
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: operative stonemasonry tools | Statement: [Square and Compasses, hasSymbolicOrigin, operative stonemasonry tools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSymbolicOrigin Context triple: [Square and Compasses, hasSymbolicOrigin, operative stonemasonry tools]
-
A.
hasSymbolicValue
Indicates that something holds meaning, significance, or representational value beyond its literal or practical function.
-
B.
hasOriginIn
chosen
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
C.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
-
D.
hasApproximateOrigin
Indicates that an entity originates from a source or location that is known only approximately rather than precisely.
-
E.
hasSymbolLocation
Indicates that a symbol is associated with or positioned at a specific location.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0282d4d08190b754cda7683408c4 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.