Triple
T24744180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Objeto ativo (Active Object) |
E618648
|
entity |
| Predicate | shapeUsage |
P1464
|
FINISHED |
| Object | rectilinear forms |
—
|
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: rectilinear forms | Statement: [Objeto ativo (Active Object), shapeUsage, rectilinear forms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shapeUsage Context triple: [Objeto ativo (Active Object), shapeUsage, rectilinear forms]
-
A.
shapePart
Indicates that one entity is a component or sub-part of the overall shape or geometric structure of another entity.
-
B.
shapeRequirement
Indicates that one entity imposes or specifies a required shape or geometric form that another entity must conform to.
-
C.
shape
chosen
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
-
D.
shapesValuesOf
Indicates that one entity influences or determines the characteristics, parameters, or magnitude of another entity’s values.
-
E.
shapeInfluencedBy
Indicates that the form or outline of one entity is affected, determined, or modified by another entity or factor.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:20 a.m.