Triple
T6202024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jennings family |
E138655
|
entity |
| Predicate | propertyUse |
P46693
|
FINISHED |
| Object | copra production (historically) |
—
|
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: copra production (historically) | Statement: [Jennings family, propertyUse, copra production (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyUse Context triple: [Jennings family, propertyUse, copra production (historically)]
-
A.
propUsed
Indicates that a particular property or attribute is utilized or applied in a given context or situation.
-
B.
usesProp
chosen
Indicates that one entity employs, utilizes, or makes use of a particular property, resource, or object in performing an action or fulfilling a function.
-
C.
partOfUse
Indicates that something functions as a component or constituent within the use or application of something else.
-
D.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
E.
property
Indicates that one entity possesses, is characterized by, or has an attribute or quality associated with 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062559bcc81908942bb4d25fe8158 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.