Triple
T31959848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fana |
E816005
|
entity |
| Predicate | mayBeConnectedTo |
P107489
|
FINISHED |
| Object | Roman concepts of sacred groves |
—
|
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: Roman concepts of sacred groves | Statement: [Fana, mayBeConnectedTo, Roman concepts of sacred groves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeConnectedTo Context triple: [Fana, mayBeConnectedTo, Roman concepts of sacred groves]
-
A.
plannedToBeConnectedTo
Indicates that one entity is intended or scheduled to be linked or joined with another entity in the future.
-
B.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
C.
hasConnectionPotential
Indicates that there exists a possibility or capacity for a meaningful connection or relationship to form between the entities.
-
D.
canBeLinkedTo
chosen
Indicates that one entity has the potential or capability to be connected or associated with another entity.
-
E.
partlyConnectedBy
Indicates that two entities are linked or joined by something in an incomplete, partial, or not fully continuous way.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 12:08 a.m.