Triple
T3383047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Society for Cultural Anthropology |
E71230
|
entity |
| Predicate | FieldsightsAccess |
P47130
|
FINISHED |
| Object | open access |
—
|
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: open access | Statement: [Society for Cultural Anthropology, FieldsightsAccess, open access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FieldsightsAccess Context triple: [Society for Cultural Anthropology, FieldsightsAccess, open access]
-
A.
leadNation
Indicates that one entity holds the primary leadership role or governing authority over a nation.
-
B.
oversightTools
Indicates that certain tools or mechanisms are used to monitor, review, or supervise the actions or performance of an entity.
-
C.
usesCaseManagementSystem
Indicates that an entity makes use of a case management system to organize, track, or handle cases or workflows.
-
D.
teamContext
Indicates that an entity is considered or interpreted within the scope, structure, or circumstances of a particular team.
-
E.
associatedFort
Indicates that one entity is connected or linked to a particular fort, typically as its related or corresponding fortification.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5eb0d188190a94415498ba81c11 |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada527ff308190813a7ffdcdec4322 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:14 p.m.