Triple
T3553276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuscarora |
E75158
|
entity |
| Predicate | traditionalMaterial |
P50559
|
FINISHED |
| Object | hemp |
—
|
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: hemp | Statement: [Tuscarora, traditionalMaterial, hemp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalMaterial Context triple: [Tuscarora, traditionalMaterial, hemp]
-
A.
buildingMaterialTradition
Indicates the customary or historically established use of particular materials in the construction of a building or structure.
-
B.
traditionalCraft
Indicates that an entity is associated with or practices a craft or skill that is rooted in long-established, culturally transmitted traditions.
-
C.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
D.
thematicMaterial
Indicates that one entity serves as the primary recurring idea, motif, or thematic content that is developed or referenced by another entity.
-
E.
material
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
- F. None of above. chosen
Provenance (4 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc05394888190b59fafda97b49beb |
completed | March 8, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adba25c66c81909a05a97327828c41 |
completed | March 8, 2026, 6:04 p.m. |
Created at: March 8, 2026, 3:20 p.m.