Triple
T16769469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rano Raraku |
E407553
|
entity |
| Predicate | materialSuitability |
P18991
|
FINISHED |
| Object | tuff suitable for carving |
—
|
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: tuff suitable for carving | Statement: [Rano Raraku, materialSuitability, tuff suitable for carving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialSuitability Context triple: [Rano Raraku, materialSuitability, tuff suitable for carving]
-
A.
lessSuitableFor
Indicates that one entity is comparatively less appropriate, effective, or fitting than another for a given purpose, context, or condition.
-
B.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
C.
isSuitableFor
chosen
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
-
D.
featuresMaterialType
Indicates that an entity is characterized by or incorporates a specific type of material.
-
E.
colorCompatibility
Indicates whether the colors associated with the entities can be used together harmoniously or without conflict.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b0356a9c8190b316cd00223e7537 |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.