Triple
T30616822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archaeocyatha |
E779335
|
entity |
| Predicate | relationshipToSponges |
P204154
|
FINISHED |
| Object | sponge-like |
—
|
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: sponge-like | Statement: [Archaeocyatha, relationshipToSponges, sponge-like]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToSponges Context triple: [Archaeocyatha, relationshipToSponges, sponge-like]
-
A.
relationshipToPoro
Indicates the type or nature of a relationship that an entity has to a Poro.
-
B.
relationshipToCreature
Indicates a specified type of relational connection that one entity has toward a particular creature.
-
C.
relationshipToPurpleTentacle
Indicates a relationship in which one entity stands in a defined connection (such as kinship, allegiance, or association) to the entity known as PurpleTentacle.
-
D.
relationshipToMelibea
Indicates a character’s specific type of personal or emotional relationship toward Melibea.
-
E.
relationshipWithAtlantis
Indicates a relationship or association that an entity has with Atlantis, such as connection, involvement, or relevance to it.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0338d1074481909541e6150307e7f8 |
completed | May 12, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_6a03386e7da08190b533cb0e908503dd |
completed | May 12, 2026, 2:25 p.m. |
| PDg | Predicate description generation | batch_6a0338d05cac819081445b6c5b32725d |
completed | May 12, 2026, 2:27 p.m. |
Created at: April 29, 2026, 8:26 p.m.