Triple
T29670002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encruzado |
E750640
|
entity |
| Predicate | structureComponents |
P70318
|
FINISHED |
| Object | good acidity |
—
|
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: good acidity | Statement: [Encruzado, structureComponents, good acidity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structureComponents Context triple: [Encruzado, structureComponents, good acidity]
-
A.
formationComponents
chosen
Indicates that one entity is composed of, or structurally includes, the other entities as its constituent parts or components.
-
B.
structurePartOf
Indicates that one structure is a constituent or component of a larger, encompassing structure.
-
C.
structureConstants
Indicates that the given values are the structure constants specifying how basis elements of an algebra (or Lie algebra) multiply or bracket to produce linear combinations of other basis elements.
-
D.
componentCC
Indicates that one entity is a component or constituent part of another entity within a coordinated or composite construction.
-
E.
component3
Indicates that one entity is the third component or sub-part within a larger composite structure or system involving another entity.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f671c69b348190807d83fe1f81946f |
completed | May 2, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:04 p.m.